-
Notifications
You must be signed in to change notification settings - Fork 40
Moving BuildSignPodManager from the pod to the buildsign package
#1035
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Moving BuildSignPodManager from the pod to the buildsign package
#1035
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: yevgeny-shnaidman The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for kubernetes-sigs-kmm ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1035 +/- ##
==========================================
- Coverage 79.09% 73.30% -5.80%
==========================================
Files 51 73 +22
Lines 5109 6214 +1105
==========================================
+ Hits 4041 4555 +514
- Misses 882 1471 +589
- Partials 186 188 +2 ☔ View full report in Codecov by Sentry. |
|
I would rename the commit title to And also updating the commit message accordingly. |
|
Do you plan to remove the |
Yes |
BuildSignPodManager interface is used only by the build and sign packages. Since we are moving into buildsign package, it make sense to move that interface there, especially as it is a porting layer
6f4867f to
dffe22a
Compare
Fixed |
pod to the buildsign package
|
/lgtm |
Adapt deployment files and tests. Upstream-Commit: 5665c56
BuildSignPodManager interface is used only by the build and sign packages.
Since we are moving into buildsign package, it make sense to move that
interface there, especially as it is a porting layer